Received: from apakabar.cc.columbia.edu (apakabar.cc.columbia.edu [128.59.35.159]) by watsun.cc.columbia.edu (8.7.3/8.7.3) with ESMTP id JAA13590 for <kermit.misc@watsun>; Wed, 28 Feb 1996 09:19:49 -0500 (EST)
Received: (from news@localhost) by apakabar.cc.columbia.edu (8.7.3/8.7.3) id JAA06339 for kermit.misc@watsun; Wed, 28 Feb 1996 09:19:46 -0500 (EST)
Path: news.columbia.edu!not-for-mail
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Need timeout facility for connected kermit session
Date: 28 Feb 1996 09:19:31 -0500
Organization: Columbia University
Lines: 26
Message-ID: <4h1o9j$d75@watsun.cc.columbia.edu>
References: <4gv52r$qlm@reader2.ix.netcom.com>
NNTP-Posting-Host: watsun.cc.columbia.edu
In article <4gv52r$qlm@reader2.ix.netcom.com>, <> wrote:
: Our users don't always end their kermit sessions
: before leaving. They forget, or a long transfer is
: still being performed. If its friday, we can have a long
: distance connection all weekend.
:
: The ckermit script input command has a timeout value
: so that something else can happen if the expected string
: is not received from a remote site.
:
: Is their a way to set an inactivity timeout so that we
: can drop the line after a transfer has finished or if an
: interactive session has no keyboard/terminal activity for
: a while.
:
Presently there is no way to do this in a client that is
being used interactively. If it's running under script
control, of course, it can be programmed to do anything you
want.
However, note that in these days of overloaded online services,
most places your users would dial into probably have their
own idle timeouts, and probably several levels of them
